Autogenerated play lists from search criteria

ABSTRACT

A method and apparatus for automatically creating a play list from search criteria. A user inputs at least one search parameter for a store of music files. The player then builds a search query from the search parameter and any other search parameters entered. The query is stored in such a manner that the query is associated with a particular play list name. When the user desires to play that play list, the entry of the play list name causes the query to be executed and a list of objects is obtained. The list of objects may in turn contain other queries, which are then executed as well.

BACKGROUND

[0001] 1. Field

[0002] This disclosure relates to digital music devices, more particularly to methods for managing play lists in those music devices.

[0003] 2. Background

[0004] With the advent of digital music devices, such as MP3 (Moving Pictures Experts Group, Audio Layer 3) players, users now have many configuration features available to them. Digital music players produce music from digital files stored in a memory on the player. The digital files are generally downloaded to the player from a host computer or network while the player is in communication with the host. The player may be portable, a home music system or mounted in a vehicle, as examples.

[0005] Many manufacturers of these types of players have made management of the music on the devices more user-friendly. Since the player has to be connected to a host computer or network, many of the players rely upon the intelligence of the host to configure their player. Configuration choices, such as selection of music to be loaded onto the player, as well as various means for organizing the music, are now available to these users through the host.

[0006] Play lists allow users to organize their music into ‘themed’ lists, such as by artist, year or type of music. Typically, users build a play list by manually selecting the appropriate files from their music selection. In some instances, users can sort their music files by a certain attribute. This may allow the selection of the files more convenient. The play lists are typically created on the host and the files are then downloaded into the player.

[0007] Some larger players, such as those in the home or in a vehicle, may have the capability to allow the user to create play lists on the player. Once the user has selected the files for a certain play list, the play list is saved. The user can then select this play list in the future.

[0008] When the player executes a play list, it plays all of the song in the list residing on the player. If new music is added to the player, the user must manually update the play list to include the new files. If the user does not remember the criteria used to create the play list, the user may have to recreate the list manually. Both of these processes are inconvenient, and even more so if the user has to reconnect to the host computer or network to perform these tasks.

[0009] It would be useful to allow users to perform these types of functions on the player and to store the play list criteria in such a manner as to automatically update them.

SUMMARY

[0010] One aspect of the disclosure is a method for automatically creating a play list from search criteria. A user inputs at least one search parameter for a store of music files. The player then builds a search query from the search parameter and any other search parameters entered. The query is stored in such a manner that the query is associated with a particular play list name. When the user desires to play that play list, the entry of the play list name causes the query to be executed and a list of objects is obtained. The list of objects may in turn contain other queries, which are then executed as well. The end result is a list of music files to be played.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The invention may be best understood by reading the disclosure with reference to the drawings, wherein:

[0012]FIG. 1 shows a digital audio device, in accordance with the invention.

[0013]FIG. 2 shows one embodiment of a user interface allowing a user to enter search criteria, in accordance with the invention.

[0014]FIG. 3 shows a flowchart of one embodiment of a method to provide automatically generated play lists from search criteria, in accordance with the invention.

[0015]FIG. 4 shows a flowchart of one embodiment of a method to automatically update a play list from a stored query, in accordance with the invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

[0016]FIG. 1 shows one example of a digital music player. The player could be a home player, such as would be found as part of a home sound system, a vehicular system such as a car or boat music system, or a portable player. Depending upon the environment for which the player is intended, various features and options may differ from one player to the next. However, typically a player in accordance with the invention will have some minimum components as shown in FIG. 1.

[0017] The player 10 has a panel upon which is a user interface, shown here as comprising a display 12, control buttons 14, 16 and 18 and possibly having an alphanumeric keypad 20. The control buttons may be of many different types, including push buttons, radio dials or sliders, although push buttons are shown here. The control buttons allow the user to control the playing of the music as well as to respond to items on the display 12.

[0018] The player typically has some sort of processor 26 that manages the user interface, accesses the music files and performs the necessary conversion to turn the digital information stored in the file into audio signals. Players also typically either have speakers or a headphone jack, not shown here. The processor accesses the files from the memory 22. In one embodiment of the invention, the files are organized into a database 24, which may reside in a separate memory or may be a portion of the same memory that stores the music files. For purposes of this discussion, and greater ease in understanding the invention, the database will be referred to here as a separate entity from the memory in which the music files are stored.

[0019] The database 24 generally comprises a list of the names of the music files and at least one field that defines an attribute of those files. For example, the database may have a list of files and the recorded year. The database can be searched by either the name or the year. The example of recorded year is merely intended to be illustrative. Many other attributes may be used, including multiple attributes per file.

[0020] The database of music files also provides the capability for the user to define and save play lists in a more automated fashion. Currently, users typically have to specify each file that is to be added to a play list. For example, Creative Labs™ has a product it includes with some of its digital music players, referred to as a ‘jukebox.’ Similarly, RealNetworksTm has a product that can be downloaded from their web site titled ‘RealJukebox™.’ These products allow users to organize their music files into play lists for easy access later, but very little automation is provided for organizing these play lists.

[0021] For example, a user wants to create a play list. In some instances, the user must access the jukebox view on a PC or other host. The user selects from a series of pull-down menus and option buttons. A typically process would be as follows. The user selects “Create Play List” from a list of options and then is prompted to provide a name for the play list. The user then goes through the entire music collection available that the jukebox application has been able to locate on the host and manually selects the files to be added to the new play list. Once finished, the user then selects an option such as ‘Add to Play List.’ The play list is then created from those files.

[0022] If the user wants to add other tracks to the play list, the user has to manually sort through the music collection again and select files to be added. If new music has been added to the PC or the player, the user may have to manually compare the current play list to the possible files to determine if the play list is up to date with the new music on the PC or player. This is inconvenient and time consuming.

[0023] Using the player of FIG. 1, however, it is possible to provide users with a user interface that allows them to automate the search and selection process. Further, it provides a process by which the automated search and selection process can be stored in a query format. Referring now to FIGS. 2 and 3, a possible user interface facilitating the methods of the invention can be discussed. It should be noted that the examples below discuss the user interface as being on the player. It is also possible that the user interface is located on the host, either a computer or network, as examples.

[0024] In FIG. 3, at 40, the process begins with reception of a user input. The user input is comprised of at least one search parameter. This can be seen by referring to FIG. 2. The display 12 now has several windows from which the user can make selections. This is an example of the player receiving the user input directly. Alternatively, the user may make selections on a host that are then transferred to the player. For example, the player is prompting the user to “Search For:” and then provides a list of parameters in window 30. The user in this example has selected the search terms “artist” as a first search term. The user can then enter the artist's name in window 36, or the player may provide a list of available artists on the player from which the user can select.

[0025] If the user wishes to refine the search further, the user may make a selection that is joined with the current search parameter by one of any number of operators. In the example of FIG. 2, the user has also selected “and year.” This will result in a list of files from a specified artist recorded in a specific year. For example, selecting “Eric Clapton” and “1977” will return a play list of all music files on the player that were originally recorded by Eric Clapton in 1977.

[0026] As can be seen in FIG. 3, the player builds a query from the user's entries from the user interface. The user interface may not provide the operators in such a manner. Other types of user interfaces may be used, including a natural language entry, voice recognition entry, point and drill type interfaces, among many others. The player would then parse the entries into a search query, such as <Artist=“Clapton”:AND:year=1977>.

[0027] It must be noted that the next stages of identifying the files using the query at 46 and the play list created from the files at 46 in FIG. 3 are optional. The user does not need to actually execute the query for it to be stored. Executing the query will be discussed in more detail with regard to FIG. 4. At 48, the player stores the query as being associated with whatever play list name the user specifies, such as that in window 39 of FIG. 2. The play list of files may never be created, unlike the current state of the art. The play list is actually stored in terms of the query built from the parameters. This has several advantages.

[0028] One advantage of this approach is the ability for the player to dynamically update the play list as new music is added to the player. As discussed previously, the addition of new music would require the user to go through the new music and determine to which play lists the new files would need to be added to update those play lists. In the embodiment of the invention discussed above, there is no inflexible list of files that are designated as the play list. If the query is run, and the new files meet the criteria in the query, the files will be part of the play list.

[0029] This is shown in FIG. 4. When the user decides to play a play list, in one embodiment of the invention, the user is actually identifying a query to be executed on the database. The user provides the play list name as an input at 50. The player accesses the query associated with that play list name at 52 and runs the query at 54. Running the query results in a list of objects at 56 where the objects are identified as having meet the requirements of the query. These files are then set up to be played as the play list. This process is transparent and the user may not even be aware that the play list that the user had set up exists only in query form.

[0030] The query itself may be a combination of queries. For example, the user may set up play list 1 with the specifications of artist A and year 2000. Play list 2 may have the files corresponding to music by artist B. Through the user interface, the user may create play list 3 as being play list 1 and play list 2. The player would interpret play list one as being something such as <Artist=“A”:AND:year=2000>. Play list 2 would then be <Artist=“B”>. Play list 3 would be stored in some manner that would combine the two queries, such as <<Artist=“A”:AND:year=2000>+<Artist=“B”>>. The player would ‘flatten’ the queries and provide a list of files. It should be noted that this last operation will more than likely be two operations, as to state Artist=A and Artist=B would be mutually exclusive. The operations will more than likely be concatenated, indicated above with the “+” sign.

[0031] Because of the ability to have multi-level queries, the list of objects may not be a list of files for immediate playing. Instead the list of objects provided at 56 may comprise an intermediate step. When the individual objects are all flattened or converted into the list of music files, the list of files would be provided at 58. Again, this may be an optional and unnecessary step, if no multi-level queries are stored as play lists. More detail can be found on multi-level, or hierarchical, play lists in copending U.S. patent application Ser. No. 09/595,818, filed Jul. 16, 2000, entitled “Digital Music Systems”, incorporated by reference herein.

[0032] In this manner, the users are provided an automated method to identify files for particular play lists. The method allows for dynamic updating of the specified files in a particular play list, transparent to the user. It also allows the storage of the play lists in terms of a query rather than an entire list of files.

[0033] Thus, although there has been described to this point a particular embodiment for a method and apparatus for automatically generating play lists from search criteria in music players, it is not intended that such specific references be considered as limitations upon the scope of this invention except in-so-far as set forth in the following claims. 

What is claimed is:
 1. A method for creating an automatic play list, the method comprising: a) receiving input from a user, wherein the input identifies at least one search parameter for a store of music files; b) building a query from the at least one search parameter; and c) storing the query such that the query is associated with a play list name.
 2. The method of claim 1, wherein the method further comprises identifying files using the query and creating a play list from those files.
 3. The method of claim 1, wherein the user input is received from a user interface on a player.
 4. The method of claim 1, wherein the user input is received from a user input on a host.
 5. The method of claim 1 wherein the user input is in natural language format.
 6. The method of claim 1, wherein building the query further comprises parsing out the user input into a query string.
 7. The method of claim 1, wherein the query further comprises a multi-level query.
 8. A method of executing a play list query, the method comprising: a) receiving an input from a user, wherein the input identifies a play list name; b) accessing a query associated with the play list name; and c) executing the query to obtain a list of objects.
 9. The method of claim 8, wherein the method further comprises converting the list of objects to a list of music files.
 10. The method of claim 8, wherein the list of objects is a list of music files.
 11. A digital music device, comprising: a) a memory to store music files; b) a database to store information associated with the music files; and c) a processor, configured to: i) receive an input from a user, wherein the input identifies at least one search parameter for a store of music files; ii) build a query from the at least one search parameter; and iii) store the query such that the query is associated with a play list name.
 12. The device of claim 11, wherein the database resides in a portion of the memory used to store music files.
 13. The device of claim 11, wherein the device further comprises a user interface operable to receive the input from the user directly.
 14. An article containing machine-readable code that, when executed, causes a machine to: a) receive input from a user, wherein the input identifies at least one search parameter for a store of music files; b) build a query from the at least one search parameter; and c) store the query such that the query is associated with a play list name.
 15. The article of claim 14 wherein the article is one of the group comprised of: a downloadable file, a diskette, or a compact disc.
 16. The article of claim 14, wherein the article contains further code that, when executed, causes the machine to identify files using the query and create a play list from the files.
 17. An article containing machine-readable code that, when executed, causes a machine to: a) receive an input from a user, wherein the input identifies a play list name; b) access a query associated with the play list name; and c) execute the query to obtain a list of objects.
 18. The article of claim 17, wherein the article contains further code that, when executed, causes the machine to convert the objects to a list of music files.
 19. The article of claim 17, wherein the list of objects is a list of music files.
 20. A digital music device, comprising: a) a means for storing music files; b) a means for storing information associated with the music files; and c) a means for: i) receiving an input from a user, wherein the input identifies at least one search parameter for a store of music files; ii) building a query from the at least one search parameter; and iii) storing the query such that the query is associated with a play list name. 